|
2020-11-19 16:50 developer |
|
|
|
Hi Jason, Could you describe more about this issue ? What do you mean by Power key not working ? From log files, system does receives "Power" key event and go to sleep mode. In main.log.2 and main.log.3, there are 2 power off/on events. Each time system receives "Power off/on", there is a HDMI plug event. I think it works well. I don't know what kind of keyword to check since many things are done by middleware. I also do test on Android P release(v15.520.08), LED will flash if you press any RCU key even STB is in standby mode. The behavior is controlled by TVStorm. One more thing, I think user press many times of Power key. But these keyevents are not shown in main.log.* files. From uptime.txt and dmesg.txt, STB is on around 10:20. However, main.log.* only record messages from 10:39 to 10:40. Below is key events I found in "dmesg.txt" for your reference. ===== key down events in dmesg.txt ==== [ 876.268975] key down 116 [ 890.354267] key down 116 [ 897.697436] key down 116 [ 904.776939] key down 116 [ 911.969798] key down 116 [ 931.304777] key down 116 [ 954.464866] key down 116 [ 964.792657] key down 116 [ 971.962911] key down 116 [ 981.510403] key down 116 [ 988.027907] key down 116 [ 995.047927] key down 116 [ 1002.555692] key down 116 [ 1011.900729] key down 116 [ 1018.935882] key down 116 [ 1032.518604] key down 116 [ 1039.306152] key down 116 [ 1053.061188] key down 116 [ 1061.371351] key down 116 [ 1076.431421] key down 116 [ 1081.906577] key down 116 [ 1090.464187] key down 116 [ 1098.106451] key down 116 [ 1106.551923] key down 116 [ 1112.402089] key down 116 [ 1122.384691] key down 116 [ 1129.224790] key down 116 [ 1137.924877] key down 116 [ 1143.797416] key down 116 [ 1150.442008] key down 116 [ 1167.565099] key down 116 [ 1174.224903] key down 402 [ 1175.222700] key down 402 [ 1177.015894] key down 116 [ 1183.862878] key down 116 [ 1192.862932] key down 402 [ 1196.882994] key down 116 [ 1202.358012] key down 116 [ 1208.253442] key down 115 [ 1211.388387] key down 252 [ 1212.700830] key down 402 [ 1214.020711] key down 115 [ 1214.485785] key down 115 [ 1215.535854] key down 114 [ 1215.820614] key down 114 [ 1216.113464] key down 114 [ 1216.413267] key down 114 [ 1216.713574] key down 114 [ 1218.565604] key down 114 [ 1222.720545] key down 227 [ 1223.028774] key down 2 [ 1223.381102] key down 2 [ 1223.778527] key down 10 [ 1224.168655] key down 232 |
|
|
hi kerwin I will check it again.. but I guess STB don't wake up by RCU. You think don't find any clue in a log. I also do test on Android P release(v15.520.08), LED will flash if you press any RCU key even STB is in standby mode. --> below comment come from your test or from SKB voc. it is confused about your comment. additionally,,, two sentence don't match up meanings. please explain it again. --> But these keyevents are not shown in main.log.* files. -->However, main.log.* only record messages from 10:39 to 10:40. |
|
|
Hi Jason, >> I also do test on Android P release(v15.520.08), LED will flash if you press any RCU key even STB is in standby mode. >> --> below comment come from your test or from SKB voc. >> it is confused about your comment. [Kerwin]: You can use a Smart3 with Android P release to verify by yourself. >> additionally,,, two sentence don't match up meanings. please explain it again. >> --> But these keyevents are not shown in main.log.* files. >> -->However, main.log.* only record messages from 10:39 to 10:40. [Kerwin]: I replies these key events are found in "dmesg.txt", not main.log.* files. Please read replies again. files_in_report_20201119.png (16,919 bytes) |
- yk.jung ( (ALTech) Younkwang Jung ) developer
